N to n money transfers

ABSTRACT

Various methods, systems, and devices are described for performing money transfers to one or more payees from one or more payors using a money transfer system. A party, such as a payor, a payee, or a third party may create a set of payee rules. The same or a different party may also create a set of payor rules. The payee rules may comprise conditions which, when satisfied, permit a payee to receive funds from a funds pool. The payor rules may comprise conditions which, when satisfied, permit a payor to provide funds to the funds pool. The money transfer system may determine whether requests from a payor and a payee comply with the payor rules and the payee rules, respectively. Based on the determination, the payor and/or payee may be permitted to complete their requested transaction, or their transaction may be denied.

RELATED APPLICATIONS

The present application claims priority to and is a continuation of U.S.patent application Ser. No. 12/841,333, filed Jul. 22, 2010, andentitled “N TO N MONEY TRANSFERS,” the entire contents of which areincorporated by reference herein for all purposes.

BACKGROUND OF THE INVENTION

A person or other entity (collectively referred to as a party) maydesire to send money to multiple other parties. Typically, this mayinvolve the party conducting multiple money transfer transactions. Eachof these money transfer transactions may need to be conductedindependently from each other. Further, each of these transactions mayinvolve the party sending funds to repeatedly provide the same pieces ofinformation necessary to conduct each money transfer transaction.

Further, multiple parties may desire to send money to the same party.Again, such a situation may require each money transaction to beconducted independently from each other. Each of these transactions mayinvolve the party sending the funds to repeatedly provide the same orsubstantial similar pieces of information necessary to conduct eachmoney transfer transaction.

Additionally, because money transfer transactions typically areone-to-one transactions, that is, one party to one other party, it maynot be possible for a party to define various conditions under whichsome other party is permitted to participate or be denied fromparticipating in the money transfer transaction.

BRIEF SUMMARY OF THE INVENTION

Various systems, methods, and devices are described for multiple partiesto one party money transfer transactions, one party to multiple partiesmoney transfer transactions, and multiple parties to multiple partiesmoney transfer transactions. Such arrangements may allow for moneytransfer transactions to be conducted that include multiple payors(parties sending money to one or more other parties), multiple payees(parties receiving money from one or more other parties), or both.

Besides allowing for multiple payors, multiple payees, or both toparticipate in linked money transfer transactions, various rules may beestablished that determine how payees and/or payors may participate inthe money transfer transactions. Such rules may be established by apayor, payee, or a third party. These rules may include rules such as:whether or not a party may serve as a payor, whether or not a party mayserve as a payee, maximum and/or minimum amounts of funds individualpayors are permitted to contribute, maximum and/or minimum amounts offunds that individual payees are permitted to receive, and variouspermissible payment (both from the payor and to the payee) methods.Further, some rules may establish conditions contingent on behavior byother payors and payees. For example, a rule may establish that a firstpayee may only receive half of the funds received by a second payee.Another example may be that a first payor is only permitted tocontribute funds after a second payor has contributed an amount offunds.

In some embodiments, a method for performing money transfers to aplurality of payees from a payor using a money transfer system ispresent. The method may include receiving a set of payee rules from thepayor. The payee rules may identify each payee of the plurality ofpayees. The payee rules may comprise conditions which, when satisfied,permit each payee of the plurality of payees to receive funds from afunds pool. The payee rules may comprise conditions that define anamount of funds that each payee of the plurality of payees is permittedto receive from the funds pool. The method may include storing the setof payee rules. The method may include receiving funds from the payor,wherein access to the funds by the plurality of payees is determinedusing the set of payee rules. The method may include linking the fundsreceived from the payor to the funds pool. The method may includereceiving a first request for funds from the funds pool from a firstpayee of the plurality of payees. The method may include determiningwhether the first request complies with a first subset of conditionscomprising the set of payee rules. The method may include providing afirst amount of funds from the funds pool to the first payee. The methodmay include receiving a second request for funds from the funds poolfrom a second payee of the plurality of payees. The method may includedetermining whether the second request complies with a second subset ofconditions comprising the set of payee rules. The second subset ofconditions may comprise at least one condition different from theconditions in the first subset of conditions. Also, the method mayinclude providing a second amount of funds to the second payee.

In some embodiments, the set of payee rules defines how much of thefunds from the funds pool received from the payor each payee of theplurality of payees is permitted to receive. In some embodiments, thepayee rules limit the second amount of funds provided to the secondpayee at least partially based on the first amount of funds provided tothe first payee. The first request for funds may identify a requestedamount of funds. The method may include determining that the firstrequest complies with the first subset of conditions of the payee rulesand further comprises determining whether the requested amount of fundscomplies with the first subset of conditions of the payee rules. In someembodiments, the method may include receiving following the secondamount of funds being provided to the second payee, additional fundsfrom the payor. The method may also include receiving from the payor, anindication that the payee rules apply to the additional funds receivedfrom the payor. In some embodiments, the set of payee rules may definepercentages that determine amount of funds from the funds pool permittedto be provided to each of the plurality of payees. In some embodiments,the money transfer system may comprise a plurality of agent locations.The first amount of funds may be provided to the first payee in cash ata first agent location. The second amount of funds may be provided tothe second payee in cash at a second agent location. The first agentlocation and the second agent location might be physically separateagent locations.

In some embodiments, a method for performing money transfers from aplurality of payors to a payee using a money transfer system may bepresent. The method may include receiving a set of payor rules from thepayee, wherein the payor rules comprise conditions that identifycircumstances in which the plurality of payors is permitted to providefunds to a funds pool. The method may include storing the set of payorrules. The method may include receiving a first request to provide fundsto the funds pool from a first payor of the plurality of payors to thepayee. The method may include determining whether the first requestcomplies with the set of payor rules. The method may include receivingfunds from the first payor. The funds may be received following thedetermination that the first request complies with the set of payorrules. The method may include linking the funds received from the firstpayor to the funds pool. The method may include receiving a secondrequest to provide funds to the funds pool from a second payor of theplurality of payors to the payee. The method may include determiningwhether the second request complies with the set of payor rules. Themethod may include receiving funds from the second payor, wherein thefunds are received following the determination that the second requestcomplies with the set of payor rules. Also, the method may includelinking the funds received from the second payor to the funds pool.

In some embodiments, a method for performing money transfers to aplurality of payees from a plurality of payors using a money transfersystem is presented. The method may include receiving a set of payeerules from a master party. The payee rules may identify each of theplurality of payees. The payee rules may identify circumstances in whicheach payee of the plurality of payees is permitted to receive funds froma funds pool. The payee rules may identify circumstances that define anamount of funds that each payee of the plurality of payees is permittedto receive from the funds pool. The method may include storing the setof payee rules. The method may include receiving a set of payor rulesfrom the master party. The set of payor rules may identify circumstancesin which each payor of the plurality of payors is permitted to providefunds to the funds pool. The method may include storing the set of payorrules. The method may include receiving a first request to provide afirst amount of funds from a first payor of the plurality of payors tothe funds pool. The method may include determining the first requestcomplies with the set of payor rules. The method may include receivingthe first amount of funds from the first payor, wherein the first amountof funds is received following the determination that the first requestcomplies with the set of payor rules. The method may include linking thefirst amount of funds to the funds pool. The method may includereceiving a second request to provide a second amount of funds from asecond payor of the plurality of payors to the funds pool. The methodmay include determining the second request complies with the set ofpayor rules. The method may include receiving the second amount of fundsfrom the second payor, wherein the second amount of funds is receivedfollowing the determination that the second request complies with theset of payor rules. The method may include linking the second amount offunds to the funds pool. Further, the method may include receiving afirst request for funds from the funds pool, the first request receivedbeing from a first payee of the plurality of payees. The method mayinclude determining the first request complies with the set of payeerules. The method may include providing a third amount of funds to thefirst payee from the funds pool. The method may include receiving asecond request for funds from the funds pool, the second requestreceived being from a second payee of the plurality of payees. Themethod may include determining the second request complies with the setof payee rules. Further, the method may include providing a fourthamount of funds to the second payee from the funds pool.

BRIEF DESCRIPTION OF THE DRAWINGS

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label with a dash and asecond label that distinguishes among the similar components. If onlythe first reference label is used in the specification, the descriptionis applicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 illustrates a simplified block diagram of an embodiment of amoney transfer system.

FIG. 2 illustrates a simplified block diagram of an embodiment of aone-to-many money transfer system.

FIG. 3 illustrates a simplified block diagram of an embodiment of amany-to-one money transfer system.

FIG. 4 illustrates a simplified block diagram of an embodiment of amany-to-many money transfer system.

FIG. 5 illustrates an embodiment of a method for a one-to-many moneytransfer.

FIG. 6 illustrates an embodiment of a method for a many-to-one moneytransfer.

FIGS. 7A and 7B illustrate an embodiment of a method for a many-to-manymoney transfer.

FIG. 8 illustrates an embodiment of a computer system.

DETAILED DESCRIPTION OF THE INVENTION

Various systems, methods, and devices are described for money transfertransactions that allow for the transactions to occur: from multipleparties to one party, from one party to multiple parties, and frommultiple parties to multiple parties (collectively referred to as N to Nmoney transfers). Besides allowing for multiple payors, multiple payees,or both to participate in the same money transfer transaction (or linkedmoney transfer transactions), various rules may be established thatdetermine how payees and/or payors may participate in the money transfertransaction. Such rules may be established by a payor, a payee, or athird party. These rules may allow for the party initiating the moneytransfer transaction (possibly a payor, payee, or third party) to definevarious rules that govern how and when other payors and payees mayprovide funds to or receive funds from a funds pool. These rules mayinclude rules such as: whether or not a party may serve as a payor,whether or not a party may serve as a payee, maximum and/or minimumamounts of funds individual payors are permitted to contribute, maximumand/or minimum amounts of funds that individual payees are permitted toreceive, and various permissible payment (both from the payor and to thepayee) methods. Further, some rules may establish conditions contingenton behavior by other payors and payees. For example, a rule mayestablish that a first payee may only receive half of the funds receivedby a second payee.

FIG. 1 illustrates a simplified embodiment 100 of a money transfersystem 100. Such a money transfer system may be operated by an entitysuch as WESTERN UNION and may be capable of performing a variety ofmoney transfer transactions from payors to payees. For example, moneytransfer system 100 may be capable of performing wire transfers and billpayment transactions. Other services may include the ability to issueand reload prepaid stored value cards with funds, and the ability tosend gift cards to a party (and reload such cards with funds). A wiretransfer may be made from one party to another party, and may involvecash being transferred. Money transfer system 100 may include one ormore agent locations 120, one or more websites 140, telephone operatorand/or interactive voice response (IVR) systems 150, mobile devices 160,a money transfer server system 110, a rules database 112, a transactiondatabase 114, a compliance module 116, and/or a customer database 118.

Agent locations 120 may represent various kiosks and/or other physicallocations where payors and payees may conduct money transfertransactions. For example, WESTERN UNION may have hundreds of thousandsof agent locations scattered worldwide. At agent locations 120, aperson, such as a clerk, may serve as a representative of the entityproviding the money transfer service. Payors and payees may conductmoney transfer transactions by interacting directly with an agent of themoney transfer entity at an agent location. Transactions conducted at anagent location may be conducted using a variety of different paymentmethods. For example, cash, checks, credit cards, debit cards, andstored value cards are all possible methods through which a payment maybe received from a payor or provided to a payee. Also, at an agentlocation, payors and payees may interact directly with a kiosk that ispart of the money transfer system 100. Alternatively, the agent of themoney transfer service provider may interact with the kiosk on behalf ofthe payor or payee.

Money transfer system 100 may include one or more websites. Suchwebsites may allow payors and payees to conduct money transfertransactions via the Internet. A payor may provide payment andtransaction information to money transfer system 100 via website 140.For example, a payor may provide bank account information or credit cardinformation to money transfer system 100 via website 140. Likewise,payees may receive payment sent via money transfer system 100 viawebsite 140. For example, it may be possible for a payee to provide abank account number for funds to be deposited via website 140. Website140 may also permit a payor or payee to determine the status of a moneytransfer transaction. If a payor is conducting the money transfer usinga bank account, credit card, stored value card, or using some otherpayment method besides cash, he may be able to conduct the entirepayor-side transaction using the website 140. Likewise, if the payee isreceiving the funds via a method other than cash, he may be able tocomplete his payee-side transaction using website 140. Alternatively, ifeither the payor and payee is conducting the transaction in cash, someof the information necessary to conduct the money transfer transactionmay be supplied via website 140, with the cash being transacted at anagent location of agent locations 120.

Money transfer system 100 may also include a telephone operator and/orinteractive voice response (IVR) system 150. Telephone operator and/orIVR system 150 may allow a payor and/or payee to conduct the moneytransfer transaction via a telephone call to the telephone operatorand/or IVR system 150. Payors and payees may provide the informationnecessary to conduct the money transfer transaction via the telephone,either to a human operator, or to an interactive voice response system.If a payor is conducting the money transfer using a bank account, creditcard, stored value card, or using some other payment method besidescash, he may be able to completely conduct the transaction using thetelephone operator and/or IVR system 150. Likewise, if the payee isreceiving the funds via a method other than cash, he may be able tocomplete the transaction using the telephone operator and/or IVR system150. Alternatively, if either the payor and payee is conducting thetransaction in cash, some of the information necessary to conduct themoney transfer transaction may be supplied via the telephone operatorand/or IVR system 150, with the cash being transacted at an agentlocation of agent locations 120.

Also, it may be possible to interact with money transfer system 100 viamobile devices 160. Mobile Device 160 may represent various wirelessdevices that can communicate with money transfer system 100. Forexample, Mobile Device 160 may include cellular telephones, smartphones, laptops, tablet computers, etc. Mobile devices 160 may load awebsite to interact with money transfer system 100. Alternatively,mobile devices 160 may run one or more pieces of software, such asapplications or firmware configured to allow interaction with moneytransfer system 100. Via mobile devices 160, it may be possible for apayor to transmit funds to a payee. Also, it may be possible for a payeeto receive funds via mobile devices 160. If a payor is conducting themoney transfer using a bank account, credit card, stored value card, orusing some other payment method besides cash, he may be able to completethe transaction using a mobile device of mobile devices 160. Likewise,if the payee is receiving the funds via a method other than cash, he maybe able to complete the transaction using a mobile device of mobiledevices 160. Alternatively, if either the payor and payee is conductingthe transaction in cash, some of the information necessary to conductthe money transfer transaction may be supplied via a mobile device ofmobile devices 160, with the cash being transacted at an agent locationof agent locations 120.

Agent locations 120, website 140, telephone operator and/or IVR system150, and mobile devices 160 may communicate with money transfer serversystem 110 via a network 130. Network 130 has been represented as asingle network in FIG. 1. This is for simplicity only, network 130 mayinclude several networks. Further, the network used for agent locations120 to communicate with money transfer server system 110 may bedifferent from the network used by mobile devices 160 to communicatewith money transfer server system 110. The network 130 may include oneor more public networks, such as the Internet, and one or more privatenetworks, such as a corporate intranet. Further, multiple networks maybe used to communicate with money transfer server system 110. Forexample, mobile devices 160 may use a wireless cellular provider'snetwork and the Internet to communicate with money transfer serversystem 110.

Whether a payor provides funds to the money transfer system 100 viaagent locations 120, website 140, telephone operator and/or IVR system150, or mobile devices 160, this may not affect how a payee may receivethe funds. For example, while a payor may provide funds via website 140,a payee may retrieve the funds via one of agent locations 120. It mayalso be possible for a payor to use the same entity, such as agentlocations 120, to conduct a money transfer transaction.

Money transfer server system 110 may include one or more varioussubsystems used to conduct a money transfer transaction. For example, acustomer database 118 may be present. Customer database 118 may storebiographical information about the money transfer service provider'scustomers (payors and payees).

Transaction database 114 may store information on pending and completedmoney transfer transactions. Transaction database 114 may identifyamounts of funds provided by payors, amounts of funds due to payees,payors' names, the payees' names, transaction identifiers such as moneytransfer control numbers (MTCNs), the locations where the transactionswere initiated (e.g., the website, an address of the agent location),the location of where the transaction is expected to be completed (e.g.,where the payee is expected to receive the funds), the payor's paymentmethod (e.g., cash, credit card, money order, stored value card, check,etc.), and whether or not various money transfer transactions have beencompleted or are pending.

Compliance module 116 may be used to ensure compliance with governmentregulations. For example, the money transfer service provider operatingthe money transfer system 100 may be required to comply with variousgovernment regulations (possibly varying by country) intended to preventfraudulent and/or illegal use of money transfer systems. An example of acompliance measure that the money transfer service provider may use is alist of persons that the money transfer service provider is prohibitedfrom doing business with published by the Office of Foreign AssetControl (OFAC). The money transfer service provider may be required bylaw to not do business with (e.g., as a payor or payee) personspublished on such a list. Other compliance measures may includegathering additional information about payors and payees conducting amoney transfer that exceeds a particular amount and/or is international.Money transfer transactions being conducted with cash may also includeadditional compliance measures. Therefore, depending on the location ofthe payor and payee, the amount of the money transfer, and the paymentmethod, each money transfer may be subject to varying levels ofexamination and regulation by compliance module 116.

Rules database 112 may store rules provided by payors, payees and/orthird parties that place conditions on how various money transfertransactions may be conducted. Various rules stored in rules database112 may be flexible. For example, payors, payees, and/or third partiesmay be provided with a variety of different options of how rules may bedefined. Such rules may determine who may serve as a payor and/or payee.Such rules may also define minimum and/or maximum amounts or percentagesof funds that payors may provide and/or payees may receive. Variousother conditions may also be possible, such as the order in whichmultiple payors may provide funds, or various payees may receive funds.Further, the rules may only allow various actions by payors and/orpayees based on actions of other payors and/or payees. For example, asecond payor may be required to provide a minimum of double what a firstpayor provided. Additional detail on various rules which may be presentin rules database 112 will be discussed herein.

Money transfer system 100 may be used by payors, payees, and thirdparties to conduct money transfer transactions from a single payor tomultiple payees. FIG. 2 illustrates a simplified block diagram of anembodiment 200 of a payor 210 transferring funds to multiple payees 220.In embodiment 200, payees 220-1, 220-2, and 220-n are present. This isintended to illustrate that the number of payees 220 may vary.Embodiments may include two payees, while other embodiments may includedozens of payees.

FIG. 2 illustrates payor 210 and payees 220 interacting directly withmoney transfer server system 110. This is for simplicity only. Referringback to FIG. 1, payor 210 and payees 220 may interact with moneytransfer server system 110 via agent locations 120, website(s) 140,telephone operator and/or IVR system 150, and/or mobile devices 160. Inembodiment 200, a single payor, payor 210, is sending funds to multiplepayees 220. This may involve payor 210 conducting one transaction withmoney transfer server system 110. This transaction may specify all ofthe biographical information about the payor necessary for a typicalmoney transfer transaction, such as her name, home address, and/or phonenumber. The payor may also be required to provide a signature, present apicture identification (e.g., driver's license, government issuedidentification card, passport, etc.) to verify her identity. Suchidentification information may only need to be provided once, despitemultiple payees being intended as recipients for funds.

Funds pool 240 may store the funds provided by payor 210. These fundsmay be intermingled with funds provided by other payors for othertransactions. Alternatively, funds pool 240 may contain funds maintainedseparate from funds submitted by other payors. An indication of theamount of funds in funds pool 240 may be stored in transaction database114. The funds provided by payor 210 may be linked with payee rules 230provided by payor 210. While funds pool 240 is illustrated as part ofthe money transfer server system 110, funds pool 240 may reside at athird-party institution, such as a bank.

Rules database 112 of money transfer server system 110 may comprise aset of payee rules 230. Payee rules 230 may define various restrictionsdefined by payor 210 (or some other authorized third party) thatgovern: 1) who may serve as a payee; 2) when each payee may receivefunds; 3) how much funds each payee may receive; 4) how many timesand/or how often a payee may receive funds, and/or other conditions.Payee rules 230 may be linked to the transaction and funds supplied bypayor 210.

Referring to point one, payor 210 may restrict who may serve as payees220 via payee rules 230. This may involve payor 210 providing names,addresses, phone numbers, user names, etc. of payees 220. The payor mayalso provide as a payee rule that if a particular party receives fundsas a payee, some other party may or may not serve as a payee. Such anarrangement may be useful if payor 210 wishes to send an amount of moneyto a family, and wishes to allow several members of the family to beable to access the money, but not if someone in the family has alreadyclaimed some or all of the funds.

Referring to point two, payor 210 may define rules that define when eachpayee specified in point one may access funds. These payee rules 230 mayinvolve payor 210 selecting a range of dates and/or times that permitone or more payees to receive funds. Another payee rule that payor 210may set is that a payee is only permitted to receive funds after someother predetermined condition has occurred, such as: some other payeehas received funds or a certain amount of funds of the funds pool 240has been received by other payees.

Referring to point three, payor 210 may define payee rules that definehow much funds each payee of payees 220 or payees 220 collectively arepermitted to receive. Of course, the amount of funds that payees 220 mayreceive may also be limited by the amount that payor 210 has provided tomoney transfer server system 110. Payor 210 may specify fixed maximumand/or minimum amounts that payees 220 are permitted to receive. Payor210 may also specify percentages that identify amounts of the fundsprovided by payor 210 to funds pool 240 that each of payees 220 arepermitted to receive. For example, a payor may provide $100 and specifythat each payee of payees 220 may receive 33%. Therefore, each payee ofpayees 220 may receive roughly $33. Alternatively, payor 210 may specifya different percentage for each payee of payees 220. For example, payor210 may define a payee rule that states that payee 220-1 is to receive60%, payee 220-2 is to receive 30%, and payee 220-n is to receive 10%.

Referring to point four, payor 210 may also define how many times and/orhow often a payee of payees 220 is permitted to receive funds. If payor210 provides an amount of funds to money transfer server system 110,this amount of funds may remain with money transfer server system 110until all of the funds provided by payor 210 have been received bypayees or payor 210. Payor 210 may specify that payees 220 or particularpayees are not permitted to conduct more than one money transfertransaction to receive funds per some period of time, such as once perweek. This may be particularly useful if the funds pool provided bypayor 210 has a large amount of funds in it and is intended to be slowlydistributed to payees 220 over a period of time. Payor 210 may alsodefine the number of times each of payees 220 is permitted to receivefunds. For example, payor 210 may allow payees to receive as much fundsfrom funds pool 240 as each payee desires, but are only allowed toreceive funds twice. Payor 210 may also define specific uses for thefunds that the payee may complete. For example, payor 210 may specifythat payees 220 may only complete bill payment with the funds ordirectly transfer the funds to specific retailers or types of retailers.

Payor 210 may also restrict the geographic location in which a payee mayreceive funds and/or the method through which payees may receive funds.For example, payee rules 230 may prevent payees from receiving fundswhile in a foreign country or in a resort area. Payor 210 may be able todefine specific agent locations payee must receive funds at. Payor 210may also restrict the payment method used by payees 220. For example,payor 210 may require that payees 220 receive funds directly into a bankaccount, or in cash at an agent location. Payor 210 may also specifythat the funds received by payees be used directly for bill paymenttransactions through money transfer server system 110.

As should be understood by those with skill in the art, payee rules 230may be set by payor 210 to apply to all of payees 220 or to individualpayees of payees 220. Further, while the above discusses payor 210setting payee rules 230, it should be understood that payor 210 maydelegate payee rules 230 to be set by some third party. Table 1illustrates an example of a set of payee rules 230 payor 210 (or somethird party) may set to govern how payees 220 receive funds.

TABLE 1 Payment Number of Frequency of Amount Location Methods TimerPeriod Transactions transactions Payee Name Available Availablepermitted Permitted Permitted permitted Payee 220-1 30% per U.S. OnlyAny Two weeks  1 One time transaction after funds only provided by payorPayee 220-2 Maximum of Zip code Agent Jun. 13, 2010- unlimited Once per$100 per 01852 locations, Jul. 12, 2010 week transaction cash only Payee220-n Unlimited Worldwide Agent Before 12 Once per locations, bill Aug.1, 2011 month payment only

A number of payees may be members of a group 222. In embodiment 200,payee 220-1 and payee 220-2 are members of group 222. Payor 210 may beable to set rules for a group, such as group 222, instead of settingindividual rules for payee 220-1 and payee 220-2. For example, if payor210 desires that the same rules apply to payee 220-1 and payee 220-2 butnot payee 220-n, payor 210 may be able to assign payee 220-1 and payee220-2 to group 222 and set the rules governing both payees 220-1 and220-2 once. Additionally, other conditions may be set for a group. Whilepayor 210 may not restrict the amount of funds payee 220-1 and payee220-2 may receive, payor 210 may restrict the group 222 from receivingmore than $100. In such an example, if payee 220-1 received $80 frommoney transfer server system 110, this may leave a maximum of $20 thatmay be received by payee 220-2 because of the limit set on group 222.Payee 220-n, because he is not a member of group 222, may not be subjectto the $100 limit imposed on group 222.

Moreover, payee rules 230 may apply to one or more amounts of fundsprovided by payor 210. Payor 210 may set up payee rules 230 to apply toa first amount of funds that payor 210 wishes to provide to payees 220.After some or all of the funds have been disbursed to payees 220, payeerules 230 may be retained for use as a template for future transactionsto payees 220 or some other payees. This may allow payor 210 at somefuture time to provide additional funds and to specify that payee rules230 again apply. As should be understood, using any of the accessmethods discussed in relation to FIG. 1 (agent locations 120, websites140, telephone operator and/or IVR system, and/or mobile devices 160),payor may create and/or modify payee rules 230.

If a payee of payees 220 attempts to receive funds using money transferserver system 110 and the payee's request satisfies all applicable payeerules 230, the payee may receive the funds. If the payee's request doesnot satisfy all applicable payee rules 230, the payee may be informed ofwhat rule was not satisfied. Alternatively, payor 210 may desire some orall payor rules 230 remain secret. As such, the payee may not be madeaware as to why her request for funds did not satisfy payee rules 230.

While FIG. 2 illustrates a one payor to multiple payee arrangement, FIG.3 illustrates a simplified block diagram of an embodiment 300 ofmultiple payors 310 transferring funds to a single payee 320. Embodiment300 may also use the money transfer server system 110. However, asopposed to storing a set of payee rules, money transfer server system110 may store a set of payor rules 330. In embodiment 300, payee 320 maydefine the payor rules 330 that payors 310 must satisfy in order toprovide funds to funds pool 240 which is accessible by payee 320. Asillustrated, three payors are present: payor 310-1, payor 310-2, andpayor 310-n. In other embodiments, two payors may be present, as maydozens of payors be present.

Embodiment 300 permits the reverse situation as embodiment 200: payee320 may define payor rules 330 that payors 310 must satisfy in order toprovide funds to payee 320 via funds pool 240. As opposed to havingpayor rules defined by payee 320, a third party may define payor rules330. Payee 320 may provide biographical information and othertransaction information to initiate the process, such as the payee'sname, address, location, phone number, bank account number, etc.

Rules database 112 of money transfer server system 110 may comprise aset of payor rules 330. Payor rules 330 may define various restrictionsdefined by payee 320 (or some other authorized third party) thatgovern: 1) who may serve as a payor; 2) when each payor may receivefunds; 3) how much funds each payor may provide; 4) how many timesand/or how often a payor may provide funds, and/or other conditions.Payor rules 330 may be linked to the transaction initiated by payee 320and funds supplied by payors 310.

Referring to point one, payee 320 may restrict who may serve as payors310 via payor rules 330. This may involve payee 320 providing names,addresses, phone numbers, user names, etc., of payors 310. The payee mayalso provide as a payor rule that if a particular party provides fundsas a payor, some other party may not serve as a payor. Such anarrangement may be useful if payee 320 wishes to receive an amount ofmoney from a family, and wishes to allow several members of the familyto be able to provide the money, but not if someone in the family hasalready provided some or all of the funds.

Referring to point two, payee 320 may define rules that define when eachpayor specified in point one may provide funds. These payor rules 330may involve payee 320 selecting a range of dates and/or times thatpermit one or more payors to provide funds. Another payor rule thatpayee 320 may set is that a payor is only permitted to provide fundsafter some other predetermined condition has occurred, such as: someother payor has (or has not) provided funds and a certain amount offunds of the funds pool 240 has (or has not) been provided by payors.

Referring to point three, payee 320 may define payor rules 330 thatdefine how much funds each payor of payors 310 or payors 310collectively are required to provide. Payee 320 may specify fixedmaximum and/or minimum amounts that payors 310 are required to provide.Payee 320 may also specify percentages that identify amounts of thefunds that must be provided by each payor of payors 310 to funds pool240. For example, a payee may specify that $90 is to be provided intotal and specify that each payor of payors 310 must provide 33.33%.Therefore, each payor of payors 310 must provide roughly $30.Alternatively, payee 320 may specify a different percentage for eachpayor of payors 310. For example, payee 320 may define a payor rule thatstates that payor 310-1 is to provide 60%, payor 310-2 is to provide30%, and payor 310-n is to provide 10%. Of course, this may becontingent on each payor agreeing to the request from payee 320 andactually providing those funds. Alternatively, the payor maypreauthorize transactions to payee 320 and provide some amount of fundsto money transfer server system 110 that may automatically provide fundsto payee 320 in accordance with payor rules 330.

Referring to point four, payee 320 may also define how many times and/orhow often a payor of payors 310 is permitted to provide funds. If payee320 requests an amount of funds from payors 310, this amount of fundsmay remain with money transfer server system 110 until all of the fundsprovided by payors 310 has been received from the payors 310. If a payorof payors 310 does not provide funds within a period of time, thetransaction may be declared void, and each payor receives all or aportion of her funds back. Payee 320 may specify that payors 310 orparticular payors are not permitted to provide funds more (or less)often than some time period, such as once per week. If a payor violatesthe rule, he may be barred from providing future funds or othertransaction may be voided, such as other payors of payors 310 mayreceive the funds they provided back. This may be particularly useful ifthe payors had each agreed to provide funds to the payee as long as eachpayor fulfilled his obligation, but one payor did not satisfy hisobligation.

Payee 320 may also restrict the geographic location in which a payor mayprovide funds and/or the method through which a payor may provide funds.For example, payor rules 230 may prevent payors from providing fundsusing a credit card. Payor 210 may be able to define specific agentlocations payee must receive funds at. Payor 210 may also restrict thepayment method used by payees 220. For example, payor 210 may requirethat payees 220 receive funds directly into a bank account, or in cashat an agent location. Payor 210 may also specify that the funds receivedby payees be used directly for bill payment transactions through moneytransfer server system 110.

As should be understood by those with skill in the art, payor rules 330may be set by payee 320 to apply to all of payors 320 or to individualpayors of payors 310. Further, while the above discussed payee 320 setspayor rules 330, it should be understood that payee 320 may delegatepayor rules 330 to be set by some third party or a payor. Table 2illustrates an example of a set of payor rules 330 payee 320 may set togovern how payors 310 may provide funds.

TABLE 2 Payment Number of Frequency of Amount to Locations Methods TimePeriod Transactions transactions Payer Name be provided allowablepermitted Permitted Permitted permitted Payor 310-1 Minimum of WorldwideAny Anytime  1 One time $500 only Payor 310-2 Maximum of U.S. Only AgentJun. 13, 2010- unlimited Once per $1000 locations, Jul. 12, 2010 weekcash only Payor 310-n Double Zip code: Website only, Before 12 Once peramount 80304 direct from a Aug. 1, 2010 day provided by bank accountPayor 310-1

The payor rules of Table 2 may also include a restriction that if thetotal amount received by payors 310 is not greater than a certain amountby a certain date, each payor receives his funds back. Or, as anotherexample, if one of the payors 310 fails to satisfy the payor rules andprovide a payment by a certain time, the entire transaction may bevoided and each payor may receive some or all of his funds back. A feemay be retained by the money transfer service provider operating moneytransfer server system 110 regardless of the outcome of the transaction,or only if it is successfully completed to the payee.

Further, a number of payors may be members of a group 312. In embodiment300, payor 310-1 and payor 310-2 are members of group 312. Payee 320 maybe able to set rules for a group, such as group 312, instead of settingindividual rules for payor 310-1 and payor 310-2. For example, if payee320 desires that the same rules apply to payor 310-1 and payor 310-2 butnot payor 310-n, payee 320 may be able to assign payor 310-1 and payor310-2 to group 312 and set the rules governing both payors 310-1 and310-2 once. Additionally, other conditions may be set for a group. Whilepayee 320 may not restrict the amount of funds payor 310-1 and payor210-2 may provide, payee 320 may restrict the group 312 from providingless than $100. In such an example, if payor 310-1 provides $40 to moneytransfer server system 110, this may leave a minimum amount of $60 thatpayor 310-2 is permitted to provide because of the limit set on group312. Payor 310-n, because he is not a member of group 312, may not besubject to the limit imposed on group 312.

Moreover, payor rules 330 may apply to one or more amounts of fundsprovided to payee 320. Payee 320 may set up payor rules 330 to apply toa first amount of funds that payee 320 wishes to receive from payors310. After some or all of the funds have been received from payors 310,payor rules 330 may be retained for use as a template for futuretransactions to payee 320 from the same or some other payors. This mayallow payee 320 at some future time to request additional funds and tospecify that payor rules 330 again apply. As should be understood, usingany of the access methods discussed in relation to FIG. 1 (agentlocations 120, websites 140, telephone operator and/or IVR system,and/or mobile devices 160), payee 320 may create and/or modify payeerules 230.

If a payor of payors 310 attempts to provide funds using money transferserver system 110 and the payor's request satisfies all applicable payorrules 330, the payee may receive the funds. If the payor's request doesnot satisfy all applicable payor rules 330, the payor may be informed ofwhat rule was not satisfied. Alternatively, payee 320 may desire some orall payee rules 330 to remain secret. As such, the payor may not be madeaware as to why her request to provide funds did not satisfy payor rules330.

Also, of note, various payors and payees may conduct transactions usingdifferent currencies. The money transfer system may be able to receivefunds in a variety of different currencies, convert the currencyreceived from the payor to a currency desired by one or more payorsusing an exchange rate. Further, a payee may request and receive fundsin a different currency from another payee.

FIG. 4 represents an embodiment where multiple payors and multiplepayees are present. In embodiment 400, both payor rules 330 and payeerules 230 may be present. Both the payor rules 330 and payee rules 230may be set by a master party 430. Master party 430 may be a payor ofpayors 410, a payee of payees 420, or a third party. Alternatively, apayor of payors 410 may set payor rules 330 or payee rules 230, while apayee of payees 420 set the payee rules 230 or payor rules 330. Masterparty 430 may delegate to a payor or payee the right to create and/ormodify the payor rules 330 and/or payee rules 230. Therefore, embodiment400 may include some or all of the previously described payor rules 330and/or payee rules 230. As such, rules may govern both the providing of,and receiving of, funds involved in a transaction conducted usingembodiment 400.

Returning to the one payor to multiple payees arrangement, a method suchas method 500 of FIG. 5 may be used. Method 500 may be use inconjunction with a system such as that presented in embodiment 200 ofFIG. 2. Alternatively, some other system may used to conduct method 500.At block 510, a set of payee rules (that governs how funds are receivedby multiple payees) may be provide by a payor. These payee rules may bethe same or similar to the various payee rules discussed in relation toembodiment 200. The payor may provide such payee rules at an agentlocation, via a website of the money transfer service provider, over thephone to a telephone operator and/or IVR system, and/or from a mobiledevice. This may involve the payor enrolling in a program offered by themoney transfer service provider to be able to specify the payee rules.In some embodiments, it may not be necessary for the payor to enrollwith the money transfer service provider. In addition to a set of payeerules, the payor may provide his biographical information. Thisinformation about the payor, such as his name, address, phone number,etc., may be necessary for each money transfer. Conducting a one-to-manytransfer may save the payor from repeatedly providing the samebiographical information.

At block 520, the payee rules may be stored by the money transferservice provider, possibly at a money transfer server system, such asthat presented in FIG. 1. These payee rules may be maintained until anassociated transaction has been completed, or indefinitely to allow apayor to reuse the same payee rules for future money transfertransactions. It may be possible for the payor to have multiple sets ofstored payee rules. For example, a payor may conduct multipletransactions with different payees and may use a different set of payeerules for each set of payees.

At block 530, the payor may provide an amount of funds that is to betransferred to the payees, assuming the payee rules are satisfied. Thesefunds may be placed in a funds pool. The funds pool may contain fundspreviously provided by the payor. For example, not all of the fundsprovided by a payor for a previous transaction may have been distributedto payees. Therefore, this amount of funds may remain accessible to thepayor to distribute. The funds received from the payor may be receivedat an agent location, via a website of the money transfer serviceprovider, over the phone to a telephone operator and/or IVR system, orfrom a mobile device. The payor may use cash, credit card, check, moneyorder, gift card, stored value card, debit card, or some other paymentmethod to provide the funds to the money transfer service provider.

At block 540, the funds received from the payor may be linked to thepayee rules created by the payor. This may involve the payor selectingthe previously created set of payee rules stored at block 520.

At block 550, a request from a payee for an amount of funds may bereceived. The payee may have been informed of the presence of funds bythe payor, or may have received a notification from the money transferservice provider, such as via email, phone, mail, etc. The requestreceived from the payee may or may not include an amount requested.

At block 560, it may be determined whether the request from the payeecomplies with the payee rules established by the payor. If the requestdoes not, the payee may be informed that her request was ineligible atblock 590. This may include informing the payee why her request wasdenied, such as, what payee rule was not satisfied by her request. Thepayee may then be presented with a corrective action to make her requestallowable. For example, this may require the payee to decrease theamount of funds she is requesting. Alternatively, if at block 560, therequest from the payee complies with the payee rules established by thepayor, the payment to the payee may proceed. If the payee was requiredto request a specific amount, this amount may also be evaluated at block560. If not, at block 570, it may be determined what the maximum amountof funds available to the payee is at that time. In some embodiments,the maximum amount of funds available to the payee may automatically beprovided. In other embodiments, the payee may be permitted to specify anamount of funds desired, up to the maximum available amount.

At block 580, the (desired) amount of funds may be provided to thepayee. The method of payment to the payee may be based on a selection ofpayment methods included in the request from the payee received at block550. Alternatively, the payee may be forced to accept the funds via aparticular method specified by the payor.

At block 595, the details of the transaction with the payee are stored.These transaction details may be used to evaluate whether other payeesare now eligible or not eligible to receive funds because the payee hasreceived a certain amount of funds.

If another payee requests funds, the method may return to block 550 andevaluate the request for this other payee. The transaction details ofthe first transaction received at block 580 may be used in conjunctionwith the payee rules to determine whether the second request complieswith the payee rules. As those with skill in the art will recognize,various numbers of payees may be used in conjunction with method 500.

In a multiple payor to one payee arrangement, a method such as method600 of FIG. 6 may be used. Method 600 may be used in conjunction with asystem such as that presented in embodiment 300 of FIG. 3.Alternatively, some other system may be used to conduct method 600. Atblock 610, a set of payor rules (that governs how funds are provided bymultiple payors) may be provided by a payee (or some other party, suchas a third party or payor). These payor rules may be the same or similarto the various payor rules discussed in relation to embodiment 300. Thepayee may provide such payor rules at an agent location, via a websiteof the money transfer service provider, over the phone to a telephoneoperator and/or IVR system, and/or from a mobile device. This mayinvolve the payee enrolling in a program offered by the money transferservice provider to be able to specify the payor rules. In someembodiments, it may not be necessary for the payee to enroll with themoney transfer service provider.

At block 620, the payor rules may be stored by the money transferservice provider, possibly at a money transfer server system. Thesepayor rules may be maintained until an associated transaction has beencompleted, or indefinitely to allow a payee to reuse the same payorrules for future money transfer transactions. It may be possible for thepayee to have multiple sets of stored payor rules. For example, a payeemay conduct multiple transactions with different payors and may use adifferent set of payor rules for each set of payors.

At block 630, a request from a payor to provide an amount of funds to afunds pool may be received. The payor may have been informed of thedesire for funds by the payee, or may have received a notification fromthe money transfer service provider, such as via email, phone, mail,etc. The request received from the payor may or may not include anamount desired to be provided.

At block 640, it may be determined whether the request from the payorcomplies with the payor rules established by the payee. If the requestdoes not, the payor may be informed that her request was ineligible atblock 695. This may include informing the payor why her request wasdenied, such as, what payor rule was not satisfied by her request. Thepayor may then be presented with a corrective action to make her requestallowable. For example, this may require the payor to increase theamount of funds she is requesting to provide. Alternatively, if at block640, the request from the payor complies with the payor rulesestablished by the payee, the payment to the payee may proceed.

At block 650, the payor may provide an amount of funds that is to betransferred to the payees, assuming the payor rules are satisfied. Thesefunds may be placed in the funds pool. The funds pool may contain fundspreviously provided by the payor or other payors. The funds receivedfrom the payor may be received at an agent location, via a website ofthe money transfer service provider, over the phone to a telephoneoperator and/or IVR system, or from a mobile device. The payor may usecash, credit card, check, money order, gift card, stored value card,debit card, or some other payment method to provide the funds to themoney transfer service provider, assuming the selected payment method isin accordance with the payor rules defined by the payee. At block 660,the funds received from the payor may be linked to the funds poolcreated to hold funds received from the various payors for the payee.

At block 665, details of the transaction between the payor and the moneytransfer service provider may be stored. These details may be used to inconjunction with the payor rules to evaluate whether some other payor ispermitted to provide an amount of funds. If another payor requests toprovide funds, the method may return to block 630 and evaluate therequest for this other payor. As those with skill in the art willrecognize, various numbers of payors may be used in conjunction withmethod 600.

At block 670, the payee may attempt to retrieve funds from the fundspool. The payee may be prevented from retrieving funds from the fundspool unless certain criteria have been satisfied. For example, the payee(or some third party) may have specified that he cannot retrieve fundsuntil all payors have contributed or some minimum amounts of funds arepresent. If these conditions are not satisfied, the request may bedenied. At block 680, the desired amount of funds may be provided to thepayee. The method of payment to the payee may be based on a selection ofpayment methods included in the request from the payee received at block670.

At block 690, the details of the transaction with the payee may bestored. Some or all of these transaction details may be provided to thepayor as proof that their funds were received by the payee.

A method such as method 700 of FIGS. 7A and 7B may be used when multiplepayors desire to transmit funds to multiple payees. Method 700 may beused in conjunction with a system such as that presented in embodiment400 of FIG. 4. Alternatively, some other system may used to conductmethod 700.

Referring to FIG. 7A, at block 705, a set of payor rules (that governshow funds are provided by multiple payors) may be provide by a masterparty. These payor rules may be the same or similar to the various payorrules discussed in relation to embodiment 300 or embodiment 400. Themaster party may provide such payor rules at an agent location, via awebsite of the money transfer service provider, over the phone to atelephone operator and/or IVR system, and/or from a mobile device. Thismay involve the master party enrolling in a program offered by the moneytransfer service provider to be able to specify the payor rules. In someembodiments, it may not be necessary for the master party to enroll withthe money transfer service provider.

At block 710, the payor rules may be stored by the money transferservice provider, possibly at a money transfer server system. Thesepayor rules may be maintained until an associated transaction has beencompleted, or indefinitely to allow the master party to reuse the samepayor rules for future money transfer transactions. It may be possiblefor the master party to have multiple sets of stored payor rules. Forexample, a master party may conduct multiple transactions with differentpayors and may use a different set of payor rules for each set ofpayors.

At block 715, a set of payee rules (that governs how funds are receivedby multiple payees) may be provide by a master party. These payee rulesmay be the same or similar to the various payee rules discussed inrelation to embodiments 200 and 400. The master party may provide suchpayee rules at an agent location, via a website of the money transferservice provider, over the phone to a telephone operator and/or IVRsystem, and/or from a mobile device. This may involve the master partyenrolling in a program offered by the money transfer service provider tobe able to specify the payee rules. In some embodiments, it may not benecessary for the master party to enroll with the money transfer serviceprovider.

At block 720, the payee rules may be stored by the money transferservice provider, possibly at a money transfer server system. Thesepayee rules may be maintained until an associated transaction has beencompleted, or indefinitely to allow the master party to reuse the samepayee rules for future money transfer transactions. It may be possiblefor the master party to have multiple sets of stored payee rules. Forexample, a master party may conduct (or manage) multiple transactionswith different payees and different payors and may use a different setof payee rules for each set of payees.

The master party of blocks 705 through 720 may be a payor, a payee, or athird party. Alternatively, the master party may be several parties. Forexample, a payor may establish the payee rules, and a payee mayestablish the payor rules. One payor of the payors may be the masterpayor that is designated to establish the payee rules. Likewise onepayee of the payees may be the master payee that is designated toestablish the payor rules. In some embodiments, the payors or a masterpayor establishes the payor rules. In some embodiments, the payees or amaster payee establishes the payee rules. Other permutations arepossible.

At block 725, a request from a payor to provide an amount of funds to afunds pool may be received. The payor may have been informed of thedesire for funds by the payee, or may have received a notification fromthe money transfer service provider, such as via email, phone, mail,etc. The request received from the payor may or may not include anamount desired to be provided.

At block 730, it may be determined whether the request from the payorcomplies with the payor rules established by the payee. If the requestdoes not, the payor may be informed that her request was ineligible atblock 745. This may include informing the payor why her request wasdenied, such as, what payor rule was not satisfied by her request. Thepayor may then be presented with a corrective action to make her requestallowable. For example, this may require the payor to increase theamount of funds she is requesting to provide. Alternatively, if at block730, the request from the payor complies with the payor rulesestablished by the payee, the payment to the payee may proceed.

At block 735, the payor may provide an amount of funds that is to betransferred to the payees, assuming the payor rules are satisfied. Thesefunds may be placed in the funds pool. The funds pool may contain fundspreviously provided by the payor or other payors. The funds receivedfrom the payor may be received at an agent location, via a website ofthe money transfer service provider, over the phone to a telephoneoperator and/or IVR system, or from a mobile device. The payor may usecash, credit card, check, money order, gift card, stored value card,debit card, or some other payment method to provide the funds to themoney transfer service provider, assuming the selected payment method isin accordance with the payor rules defined by the master party. At block740, the funds received from the payor may be linked to the funds poolcreated to hold funds received from the various payors for the payee.

At block 742, details of the transaction between the payor and the moneytransfer service provider may be stored. These details may be used to inconjunction with the payor rules to evaluate whether some other payor ispermitted to provide an amount of funds. If another payor requests toprovide funds, the method may return to block 725 and evaluate therequest for this other payor. As those with skill in the art willrecognize, various numbers of payors may be used in conjunction withmethod 700. Method 700 continues on FIG. 7B.

At block 750, a request from a payee for an amount of funds may bereceived. The payee may have been informed of the presence of funds bythe payor, or may have received a notification from the money transferservice provider, such as via email, phone, mail, etc. The requestreceived from the payee may or may not include an amount requested.

At block 755, it may be determined whether the request from the payeecomplies with the payee rules established by the master party. If therequest does not, the payee may be informed that her request wasineligible at block 770. This may include informing the payee why herrequest was denied, such as, what payee rule was not satisfied by herrequest. The payee may then be presented with a corrective action tomake her request allowable. For example, this may require the payee todecrease the amount of funds she is requesting. Alternatively, if atblock 755, the request from the payee complies with the payee rulesestablished by the master party, the payment to the payee may proceed.If the payee was required to request a specific amount, this amount mayalso be evaluated at block 755. If not, at block 760, it may bedetermined what the maximum amount of funds available to the payee is atthat time. In some embodiments, the maximum amount of funds available tothe payee may automatically be provided. In other embodiments, the payeemay be permitted to specify an amount of funds desired, up to themaximum available amount.

At block 765, the (desired) amount of funds may be provided to thepayee. The method of payment to the payee may be based on a selection ofpayment methods included in the request from the payee received at block750. Alternatively, the payee may be forced to accept the funds via aparticular method specified by the master party.

At block 775, the details of the transaction with the payee are stored.These transaction details may be used to evaluate whether other payeesare now eligible or not eligible to receive funds because the payee hasreceived a certain amount of funds.

If another payee requests funds, the method may return to block 750 andevaluate the request for this other payee. The transaction detailsstored at block 775 may be used in conjunction with the payee rules todetermine whether the second request complies with the payee rules. Asthose with skill in the art will recognize, various numbers of payeesmay be used in conjunction with method 500. Further, it should beunderstood that in method 700 one or more payors may provide funds aftera payee has received funds.

To perform the actions of the money transfer server system, the kiosksand/or any of the other previously mentioned computing devices, acomputer system as illustrated in FIG. 8 may be used. FIG. 8 provides aschematic illustration of one embodiment of a computer system 800 thatcan perform the methods provided by various other embodiments, asdescribed herein, and/or can function as the host computer system, aremote kiosk/terminal, a point-of-sale device, a mobile device, and/or acomputer system. It should be noted that FIG. 8 is meant only to providea generalized illustration of various components, any or all of whichmay be utilized as appropriate. FIG. 8, therefore, broadly illustrateshow individual system elements may be implemented in a relativelyseparated or relatively more integrated manner.

The computer system 800 is shown comprising hardware elements that canbe electrically coupled via a bus 805 (or may otherwise be incommunication, as appropriate). The hardware elements may include one ormore processors 810, including without limitation one or moregeneral-purpose processors and/or one or more special-purpose processors(such as digital signal processing chips, graphics accelerationprocessors, and/or the like); one or more input devices 815, which caninclude without limitation a mouse, a keyboard and/or the like; and oneor more output devices 820, which can include without limitation adisplay device, a printer and/or the like.

The computer system 800 may further include (and/or be in communicationwith) one or more storage devices 825, which can comprise, withoutlimitation, local and/or network accessible storage, and/or can include,without limitation, a disk drive, a drive array, an optical storagedevice, a solid-state storage device such as a random access memory(“RAM”) and/or a read-only memory (“ROM”), which can be programmable,flash-updateable and/or the like. Such storage devices may be configuredto implement any appropriate data stores, including without limitation,various file systems, database structures, and/or the like.

The computer system 800 might also include a communications subsystem830, which can include without limitation a modem, a network card(wireless or wired), an infrared communication device, a wirelesscommunication device and/or chipset (such as a Bluetooth™ device, an802.11 device, a WiFi device, a WiMax device, cellular communicationfacilities, etc.), and/or the like. The communications subsystem 830 maypermit data to be exchanged with a network (such as the networkdescribed below, to name one example), other computer systems, and/orany other devices described herein. In many embodiments, the computersystem 800 will further comprise a working memory 835, which can includea RAM or ROM device, as described above.

The computer system 800 also can comprise software elements, shown asbeing currently located within the working memory 835, including anoperating system 840, device drivers, executable libraries, and/or othercode, such as one or more application programs 845, which may comprisecomputer programs provided by various embodiments, and/or may bedesigned to implement methods, and/or configure systems, provided byother embodiments, as described herein. Merely by way of example, one ormore procedures described with respect to the method(s) discussed abovemight be implemented as code and/or instructions executable by acomputer (and/or a processor within a computer); in an aspect, then,such code and/or instructions can be used to configure and/or adapt ageneral purpose computer (or other device) to perform one or moreoperations in accordance with the described methods.

A set of these instructions and/or code might be stored on acomputer-readable storage medium, such as the storage device(s) 825described above. In some cases, the storage medium might be incorporatedwithin a computer system, such as the system 800. In other embodiments,the storage medium might be separate from a computer system (e.g., aremovable medium, such as a compact disc), and or provided in aninstallation package, such that the storage medium can be used toprogram, configure and/or adapt a general purpose computer with theinstructions/code stored thereon. These instructions might take the formof executable code, which is executable by the computer system 800and/or might take the form of source and/or installable code, which,upon compilation and/or installation on the computer system 800 (e.g.,using any of a variety of generally available compilers, installationprograms, compression/decompression utilities, etc.) then takes the formof executable code.

It will be apparent to those skilled in the art that substantialvariations may be made in accordance with specific requirements. Forexample, customized hardware might also be used, and/or particularelements might be implemented in hardware, software (including portablesoftware, such as applets, etc.), or both. Further, connection to othercomputing devices such as network input/output devices may be employed.

As mentioned above, in one aspect, some embodiments may employ acomputer system (such as the computer system 800) to perform methods inaccordance with various embodiments of the invention. According to a setof embodiments, some or all of the procedures of such methods areperformed by the computer system 800 in response to processor 810executing one or more sequences of one or more instructions (which mightbe incorporated into the operating system 840 and/or other code, such asan application program 845) contained in the working memory 835. Suchinstructions may be read into the working memory 835 from anothercomputer-readable medium, such as one or more of the storage device(s)825. Merely by way of example, execution of the sequences ofinstructions contained in the working memory 835 might cause theprocessor(s) 810 to perform one or more procedures of the methodsdescribed herein.

The terms “machine-readable medium” and “computer-readable medium,” asused herein, refer to any medium that participates in providing datathat causes a machine to operate in a specific fashion. In an embodimentimplemented using the computer system 800, various computer-readablemedia might be involved in providing instructions/code to processor(s)810 for execution and/or might be used to store and/or carry suchinstructions/code (e.g., as signals). In many implementations, acomputer-readable medium is a physical and/or tangible storage medium.Such a medium may take many forms, including but not limited to,non-volatile media, volatile media, and transmission media. Non-volatilemedia include, for example, optical and/or magnetic disks, such as thestorage device(s) 825. Volatile media include, without limitation,dynamic memory, such as the working memory 835. Transmission mediainclude, without limitation, coaxial cables, copper wire and fiberoptics, including the wires that comprise the bus 805, as well as thevarious components of the communication subsystem 830 (and/or the mediaby which the communications subsystem 830 provides communication withother devices). Hence, transmission media can also take the form ofwaves (including without limitation radio, acoustic and/or light waves,such as those generated during radio-wave and infrared datacommunications).

Common forms of physical and/or tangible computer-readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, a CD-ROM, any other opticalmedium, punchcards, papertape, any other physical medium with patternsof holes, a RAM, a PROM, EPROM, a FLASH-EPROM, any other memory chip orcartridge, a carrier wave as described hereinafter, or any other mediumfrom which a computer can read instructions and/or code.

Various forms of computer-readable media may be involved in carrying oneor more sequences of one or more instructions to the processor(s) 810for execution. Merely by way of example, the instructions may initiallybe carried on a magnetic disk and/or optical disc of a remote computer.A remote computer might load the instructions into its dynamic memoryand send the instructions as signals over a transmission medium to bereceived and/or executed by the computer system 800. These signals,which might be in the form of electromagnetic signals, acoustic signals,optical signals and/or the like, are all examples of carrier waves onwhich instructions can be encoded, in accordance with variousembodiments of the invention.

The communications subsystem 830 (and/or components thereof) generallywill receive the signals, and the bus 805 then might carry the signals(and/or the data, instructions, etc. carried by the signals) to theworking memory 835, from which the processor(s) 805 retrieves andexecutes the instructions. The instructions received by the workingmemory 835 may optionally be stored on a storage device 825 eitherbefore or after execution by the processor(s) 810.

It should be noted that the methods, systems, and devices discussedabove are intended merely to be examples. It must be stressed thatvarious embodiments may omit, substitute, or add various procedures orcomponents as appropriate. For instance, it should be appreciated that,in alternative embodiments, the methods may be performed in an orderdifferent from that described, and that various steps may be added,omitted, or combined. Also, features described with respect to certainembodiments may be combined in various other embodiments. Differentaspects and elements of the embodiments may be combined in a similarmanner. Also, it should be emphasized that technology evolves and, thus,many of the elements are examples and should not be interpreted to limitthe scope of the invention.

Specific details are given in the description to provide a thoroughunderstanding of the embodiments. However, it will be understood by oneof ordinary skill in the art that the embodiments may be practicedwithout these specific details. For example, well-known circuits,processes, algorithms, structures, and techniques have been shownwithout unnecessary detail in order to avoid obscuring the embodiments.This description provides example embodiments only, and is not intendedto limit the scope, applicability, or configuration of the invention.Rather, the preceding description of the embodiments will provide thoseskilled in the art with an enabling description for implementingembodiments of the invention. Various changes may be made in thefunction and arrangement of elements without departing from the spiritand scope of the invention.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flow diagram or block diagram. Although each maydescribe the operations as a sequential process, many of the operationscan be performed in parallel or concurrently. In addition, the order ofthe operations may be rearranged. A process may have additional stepsnot included in the figure. Furthermore, embodiments of the methods maybe implemented by hardware, software, firmware, middleware, microcode,hardware description languages, or any combination thereof. Whenimplemented in software, firmware, middleware, or microcode, the programcode or code segments to perform the necessary tasks may be stored in acomputer-readable medium such as a storage medium. Processors mayperform the necessary tasks.

Having described several embodiments, it will be recognized by those ofskill in the art that various modifications, alternative constructions,and equivalents may be used without departing from the spirit of theinvention. For example, the above elements may merely be a component ofa larger system, wherein other rules may take precedence over orotherwise modify the application of the invention. Also, a number ofsteps may be undertaken before, during, or after the above elements areconsidered. Accordingly, the above description should not be taken aslimiting the scope of the invention.

What is claimed is:
 1. A money transfer system for performing aplurality of money transfers between a plurality of payors and aplurality of payees, the system comprising: a plurality of payeecomputing devices, each said payee computing device including aprocessing unit, a memory communicatively connected with and readable bythe processing unit, and one or more input devices allowing acorresponding payee to request and receive funds from a funds pool; aplurality of payor computing devices, each said payor computing deviceincluding a processing unit, a memory communicatively connected with andreadable by the processing unit, and one or more input devices allowinga corresponding payor to provide funds into the funds pool; a rulesdatabase configured to store a set of payee rules and a set of payorrules; and a money transfer server comprising: a processing unitincluding one or more processors a memory communicatively connected withand readable by the processing unit, the memory containing instructionsthat, when executed by the processing unit, cause the processing unitto: receive a set of payee rules from a master party, wherein the set ofpayee rules identifies the plurality of payees, circumstances in whicheach payee of the plurality of payees is permitted to receive funds fromthe funds pool, and circumstances that define an amount of funds thateach payee of the plurality of payees is permitted to receive from thefunds pool; store the set of payee rules; receive a set of payor rulesfrom the master party, wherein the set of payor rules identifies theplurality of payors, circumstances in which each payor of the pluralityof payors is permitted to provide funds to the funds pool; store the setof payor rules; receive, from a first payor computing device, a firstrequest from a first payor to provide a first amount of funds into thefunds pool; determine that the first request complies with the set ofpayor rules; receive the first amount of funds from the first payor,wherein the first amount of funds are received following thedetermination that the first request complies with the set of payorrules; receive, from a first payee computing device, a second requestfrom a first payee for a second amount of funds from the funds pool;determine that the second request complies with the set of payee rules;and provide the second amount of funds to the first payee from the fundspool.
 2. The money transfer system of claim 1, wherein the payee rulesfurther comprise a rule that prevents the plurality of payees fromreceiving funds until a minimum total amount of funds has been providedby the plurality of payors into the funds pool.
 3. The money transfersystem of claim 1, the memory of the money transfer server containingfurther instructions that, when executed by the processing unit, causethe processing unit to: receive, from the first payor computing device,a third request to provide a third amount of funds to the funds pool;determine that the third request does not comply with the set of payorrules; and based on the determination, reject the third request from thefirst payor computing device to provide funds into the funds pool. 4.The money transfer system of claim 1, the memory of the money transferserver containing further instructions that, when executed by theprocessing unit, cause the processing unit to: receive, from the firstpayee computing device, a third request for a third amount of funds fromthe funds pool; determine that the third request does not comply withthe set of payee rules; and based on the determination, rejecting thethird request from the first payee for the third amount of funds fromthe funds pool.
 5. The money transfer system of claim 1, the memory ofthe money transfer server containing further instructions that, whenexecuted by the processing unit, cause the processing unit to: receive,from a second payee computing device, a third request from a secondpayee for funds from the funds pool; determine a third amount of fundsto provide to the second payee, wherein the third amount of funds isdetermined as a percentage of the second amount of funds provided to thefirst payee; and provide the determined third amount of funds to thesecond payee from the funds pool.
 6. The money transfer system of claim1, the memory of the money transfer server containing furtherinstructions that, when executed by the processing unit, cause theprocessing unit to: receive, from a second payor computing device, athird request from a second payor to provide a funds into the fundspool; determine a third amount of funds to be provided by the secondpayor, wherein the third amount of funds is determined as a percentageof the first amount of funds provided to the first payor; and receivethe determined third amount of funds from the second payor, wherein thethird amount of funds are received following the determination that thethird request complies with the set of payor rules.
 7. The moneytransfer system of claim 1, wherein the set of payee rules includes arequirement that the plurality of payees receive funds in a predefinedchronological order of payees.
 8. The money transfer system of claim 1,wherein the set of payor rules includes a requirement that the payorsprovide funds into the funds pool in a predefined chronological order ofpayors.
 9. The money transfer system of claim 1, wherein the masterparty is a payor of the plurality of payors.
 10. The money transfersystem of claim 1, wherein the master party is a payee of the pluralityof payees.
 11. A method for performing money transfers using a moneytransfer system, the method comprising: receiving, by the money transfersystem, a set of payee rules from a master party, wherein: the set ofpayee rules identifies one or more payees; the set of payee rulesidentifies circumstances in which each payee of the one or more payeesis permitted to receive funds from a funds pool; and the set of payeerules identifies circumstances that define an amount of funds that eachpayee of the one or more payees is permitted to receive from the fundspool; storing, by the money transfer system, the set of payee rules;receiving, by the money transfer system, a set of payor rules from themaster party, wherein: the set of payor rules identifies one or morepayors; and the set of payor rules identifies circumstances in whicheach payor of the one or more payors is permitted to provide funds tothe funds pool; storing, by the money transfer system, the set of payorrules; receiving, by the money transfer system and from a first payor ofthe one or more payors, a first request to provide a first amount offunds into the funds pool; determining, by the money transfer system,the first request complies with the set of payor rules; receiving, bythe money transfer system, the first amount of funds from the firstpayor, wherein the first amount of funds are received following thedetermination that the first request complies with the set of payorrules; receiving, by the money transfer system and from a first payee ofthe one or more payees, a second request for a second amount of fundsfrom the funds pool; determining, by the money transfer system, thesecond request complies with the set of payee rules; and providing, bythe money transfer system, the second amount of funds to the first payeefrom the funds pool.
 12. The method of claim 11, wherein the one or morepayees includes a plurality of payees and wherein the one or more payorsincludes a plurality of payors.
 13. The method of claim 11, wherein themaster party is a payor of the one or more payors.
 14. The method ofclaim 11, wherein the master party is a payee of the one or more payees.15. The method of claim 11, further comprising: receiving, by the moneytransfer system and from the first payor, a third request to provide athird amount of funds to the funds pool; determining, by the moneytransfer system, that the third request does not comply with the set ofpayor rules; and based on the determination, rejecting the third requestfrom the first payor to provide funds into the funds pool.
 16. Themethod of claim 11, further comprising: receiving, by the money transfersystem and from the first payee, a third request for a third amount offunds from the funds pool; determining, by the money transfer system,that the third request does not comply with the set of payee rules; andbased on the determination, rejecting the third request from the firstpayee for the third amount of funds from the funds pool.
 17. The methodof claim 11, further comprising: receiving, by the money transfer systemand from a second payee of the one or more payees, a third request forfunds from the funds pool; determining, by the money transfer system, athird amount of funds to provide to the second payee, wherein the thirdamount of funds is determined as a percentage of the second amount offunds provided to the first payee; and providing, by the money transfersystem, the determined third amount of funds to the second payee fromthe funds pool.
 18. The method of claim 11, further comprising:receiving, by the money transfer system and from a second payor of theone or more payor, a third request to provide a funds into the fundspool; determining, by the money transfer system, a third amount of fundsto be provided by the second payor, wherein the third amount of funds isdetermined as a percentage of the first amount of funds provided to thefirst payor; and receiving, by the money transfer system, the determinedthird amount of funds from the second payor, wherein the third amount offunds are received following the determination that the third requestcomplies with the set of payor rules.
 19. The method of claim 11,wherein the set of payee rules includes a requirement that the payeesreceive funds in a predefined chronological order of payees.
 20. Themethod of claim 11, wherein the set of payor rules includes arequirement that the payors provide funds into the funds pool in apredefined chronological order of payors.